Fix encrypted ZFS persistence and dcap-qvl security vulnerability #468
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Fix encrypted ZFS persistence issue: VMs with encrypted ZFS storage were reformatting the disk on every reboot. The
is_disk_initialized()check required both LUKS header AND zpool detection for encrypted ZFS, but zpool import is attempted before LUKS is opened, which always fails. Now for encrypted filesystems, we only check LUKS header presence.Fix dcap-qvl security vulnerability: Update dcap-qvl from 0.2.0 to 0.3.10 in key-provider-build/Cargo.lock to fix "Missing Verification for QE Identity" (dependabot alert Implement tdxctl remove-orphans #95).
Test plan